Method, System, and Computer Program Product for Processing a Transaction Initiated Using an Electronic Wallet

ABSTRACT

A method for processing a transaction initiated using an electronic wallet application may include storing a virtual payment device configured to initiate a transaction. A rewards inquiry may be communicated to an issuer. A rewards inquiry response may be received from the issuer containing a rewards amount associated with the virtual payment device. The rewards amount may be displayed. A transaction may be initiated with a merchant using the virtual payment device. A redemption request may be communicated to the issuer. A redemption response including an updated rewards amount may be received from the issuer and include a difference between the rewards amount and the rewards amount applied toward the transaction. A system and computer program product are also disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 18/084,663, filed Dec. 20, 2022, which is a continuation ofU.S. patent application Ser. No. 17/698,296, filed Mar. 18, 2022, nowU.S. Pat. No. 11,562,391, which is a continuation of U.S. patentapplication Ser. No. 16/375,247, filed Apr. 4, 2019, now U.S. Pat. No.11,328,316, the disclosures of which are hereby incorporated byreference in their entireties.

BACKGROUND 1. Field

The disclosure relates to electronic wallets and, in some non-limitingembodiments or aspects, to a method, system, and computer programproduct for processing a transaction initiated using an electronicwallet.

2. Technical Considerations

Certain consumers may carry multiple payment devices (e.g., credit cardsand/or debit cards) in order to initiate transactions with merchantsaccepting such forms of payment. The payment devices held by theconsumer may have been issued by the same or different issuerinstitutions. The account data for these payment devices may be storedin the consumer's electronic wallet, which may be an application ontheir mobile device (e.g., a smartphone or tablet) and/or a server.Electronic wallets may reduce the need to carry the physical paymentdevice and provide convenience at the point of sale by initiatingtransactions using the mobile device.

However, electronic wallets may not enable users to efficiently redeemrewards earned using their various payment devices. For example, someissuers of the payment devices may integrate with some individualmerchants to enable rewards redemption at the respective merchants;however, issuers are not integrated with all merchants. As a result, theuser is not able to redeem earned rewards with all merchants, but onlythose select merchants with which the issuer is integrated.

SUMMARY

Accordingly, and generally, provided is an improved method, system, andcomputer program product for processing a transaction initiated using anelectronic wallet application.

According to some non-limiting embodiments or aspects, a method forprocessing a transaction initiated using an electronic walletapplication includes: storing, in an electronic wallet application of auser device of a user, at least one virtual payment device associatedwith a payment device issued to the user by an issuer system, the atleast one virtual payment device configured to initiate at least one ofa debit and credit transaction; communicating, from the user device bythe electronic wallet application, a rewards inquiry to an issuer systemof the issuer; receiving, at the user device by the electronic walletapplication, a rewards inquiry response from the issuer system, therewards inquiry response containing a rewards amount associated with theat least one virtual payment device; displaying, in the electronicwallet application of the user device, the rewards amount associatedwith the at least one virtual payment device; initiating, with the userdevice by the electronic wallet application, a debit or credittransaction for a transaction amount with a merchant system using the atleast one virtual payment device; communicating, from the user device bythe electronic wallet application, a redemption request to the issuersystem, where the redemption request specifies at least a portion of therewards amount to be applied to the debit or credit transaction; andreceiving, at the user device by the electronic wallet application, aredemption response including an updated rewards amount from the issuersystem, where the updated rewards amount includes a difference betweenthe rewards amount and the at least the portion of the rewards amountapplied toward the debit or credit transaction.

In some non-limiting embodiments or aspects, the method may furtherinclude receiving, at the user device by the electronic walletapplication, an input indicating that the debit or credit transaction isto be processed using at least a portion of the rewards amount.Communicating the rewards inquiry to the issuer system may includecommunicating, from the user device by the electronic walletapplication, a first rewards inquiry to a transaction service providersystem of a transaction service provider associated with the at leastone virtual payment device according to a first application programminginterface, where the first rewards inquiry may cause the transactionservice provider system to generate and communicate a second rewardsinquiry to the issuer system according to a second applicationprogramming interface. The at least one virtual payment device may bestored in the electronic wallet application as a token, where the tokenmay be different from an account identifier assigned by the issuersystem to the payment device. The first rewards inquiry may include thetoken and the second rewards inquiry may include the account identifier,where generating the second rewards inquiry may include replacing thetoken of the first rewards inquiry with the account identifier to formthe second rewards inquiry. The method may further include receiving, inthe electronic wallet application of the user device, the at least onevirtual payment device from a transaction service provider systemassociated with the at least one virtual payment device before storingthe at least one virtual payment device in the electronic walletapplication of the user device. The issuer system may credit an accountof the user with the at least the portion of the rewards amount to beapplied to the debit or credit transaction during settlement of thedebit or credit transaction.

According to some non-limiting embodiments or aspects, a system forprocessing a transaction initiated using an electronic walletapplication includes at least one processor programmed or configured to:store, in an electronic wallet application, at least one virtual paymentdevice associated with a payment device issued to the user by an issuersystem, the at least one virtual payment device configured to initiateat least one of a debit and credit transaction; communicate, by theelectronic wallet application, a rewards inquiry to an issuer system ofthe issuer; receive, by the electronic wallet application, a rewardsinquiry response from the issuer system, the rewards inquiry responsecontaining a rewards amount associated with the at least one virtualpayment device; display, in the electronic wallet application, therewards amount associated with the at least one virtual payment device;initiate, by the electronic wallet application, a debit or credittransaction for a transaction amount with a merchant system using the atleast one virtual payment device; communicate, by the electronic walletapplication, a redemption request to the issuer system, where theredemption request specifies at least a portion of the rewards amount tobe applied to the debit or credit transaction; and receive, by theelectronic wallet application, a redemption response including anupdated rewards amount from the issuer system, where the updated rewardsamount includes a difference between the rewards amount and the at leastthe portion of the rewards amount applied toward the debit or credittransaction.

In some non-limiting embodiments or aspects, the at least one processormay be further programmed or configured to: receive, by the electronicwallet application, an input indicating that the debit or credittransaction is to be processed using at least a portion of the rewardsamount. Communicating the rewards inquiry to the issuer system mayinclude the at least one processor: communicating, by the electronicwallet application, a first rewards inquiry to a transaction serviceprovider system of a transaction service provider associated with the atleast one virtual payment device according to a first applicationprogramming interface, where the first rewards inquiry may cause thetransaction service provider system to generate and communicate a secondrewards inquiry to the issuer system according to a second applicationprogramming interface. The at least one virtual payment device may bestored in the electronic wallet application as a token, where the tokenmay be different from an account identifier assigned by the issuersystem to the payment device. The first rewards inquiry may include thetoken and the second rewards inquiry may include the account identifier,where generating the second rewards inquiry may include replacing thetoken of the first rewards inquiry with the account identifier to formthe second rewards inquiry. The at least one processor may be furtherprogrammed or configured to receive, in the electronic walletapplication, the at least one virtual payment device from a transactionservice provider system associated with the at least one virtual paymentdevice before storing the at least one virtual payment device in theelectronic wallet application. The redemption request may cause theissuer system to credit an account of the user with the at least theportion of the rewards amount to be applied to the debit or credittransaction during settlement of the debit or credit transaction.

According to some non-limiting embodiments or aspects, a computerprogram product for processing a transaction initiated using anelectronic wallet application includes at least one non-transitorycomputer-readable medium including one or more instructions that, whenexecuted by at least one processor, cause the at least one processor to:store, in an electronic wallet application, at least one virtual paymentdevice associated with a payment device issued to the user by an issuersystem, the at least one virtual payment device configured to initiateat least one of a debit and credit transaction; communicate, by theelectronic wallet application, a rewards inquiry to an issuer system ofthe issuer; receive, by the electronic wallet application, a rewardsinquiry response from the issuer system, the rewards inquiry responsecontaining a rewards amount associated with the at least one virtualpayment device; display, in the electronic wallet application, therewards amount associated with the at least one virtual payment device;initiate, by the electronic wallet application, a debit or credittransaction for a transaction amount with a merchant system using the atleast one virtual payment device; communicate, by the electronic walletapplication, a redemption request to the issuer system, where theredemption request specifies at least a portion of the rewards amount tobe applied to the debit or credit transaction; and receive, by theelectronic wallet application, a redemption response including anupdated rewards amount from the issuer system, where the updated rewardsamount includes a difference between the rewards amount and the at leastthe portion of the rewards amount applied toward the debit or credittransaction.

In some non-limiting embodiments or aspects, the one or moreinstructions may further cause the at least one processor to: receive,by the electronic wallet application, an input indicating that the debitor credit transaction is to be processed using at least a portion of therewards amount. Communicating the rewards inquiry to the issuer systemmay include the at least one processor: communicating, by the electronicwallet application, a first rewards inquiry to a transaction serviceprovider system of a transaction service provider associated with the atleast one virtual payment device according to a first applicationprogramming interface, where the first rewards inquiry may cause thetransaction service provider system to generate and communicate a secondrewards inquiry to the issuer system according to a second applicationprogramming interface. The at least one virtual payment device may bestored in the electronic wallet application as a token, where the tokenmay be different from an account identifier assigned by the issuersystem to the payment device. The first rewards inquiry may include thetoken and the second rewards inquiry may include the account identifier,where generating the second rewards inquiry may include replacing thetoken of the first rewards inquiry with the account identifier to formthe second rewards inquiry. The one or more instructions may furthercause the at least one processor to receive, in the electronic walletapplication, the at least one virtual payment device from a transactionservice provider system associated with the at least one virtual paymentdevice before storing the at least one virtual payment device in theelectronic wallet application. The redemption request may cause theissuer system to credit an account of the user with the at least theportion of the rewards amount to be applied to the debit or credittransaction during settlement of the debit or credit transaction.

Further embodiments or aspects are set forth in the following numberedclauses:

Clause 1: A method for processing a transaction initiated using anelectronic wallet application, comprising: storing, in an electronicwallet application of a user device of a user, at least one virtualpayment device associated with a payment device issued to the user by anissuer system, the at least one virtual payment device configured toinitiate at least one of a debit and credit transaction; communicating,from the user device by the electronic wallet application, a rewardsinquiry to an issuer system of the issuer; receiving, at the user deviceby the electronic wallet application, a rewards inquiry response fromthe issuer system, the rewards inquiry response containing a rewardsamount associated with the at least one virtual payment device;displaying, in the electronic wallet application of the user device, therewards amount associated with the at least one virtual payment device;initiating, with the user device by the electronic wallet application, adebit or credit transaction for a transaction amount with a merchantsystem using the at least one virtual payment device; communicating,from the user device by the electronic wallet application, a redemptionrequest to the issuer system, wherein the redemption request specifiesat least a portion of the rewards amount to be applied to the debit orcredit transaction; and receiving, at the user device by the electronicwallet application, a redemption response comprising an updated rewardsamount from the issuer system, wherein the updated rewards amountcomprises a difference between the rewards amount and the at least theportion of the rewards amount applied toward the debit or credittransaction.

Clause 2: The method of clause 1, further comprising: receiving, at theuser device by the electronic wallet application, an input indicatingthat the debit or credit transaction is to be processed using at least aportion of the rewards amount.

Clause 3: The method of clause 1 or clause 2, wherein communicating therewards inquiry to the issuer system comprises: communicating, from theuser device by the electronic wallet application, a first rewardsinquiry to a transaction service provider system of a transactionservice provider associated with the at least one virtual payment deviceaccording to a first application programming interface, wherein thefirst rewards inquiry causes the transaction service provider system togenerate and communicate a second rewards inquiry to the issuer systemaccording to a second application programming interface.

Clause 4: The method of any of clauses 1-3, wherein the at least onevirtual payment device is stored in the electronic wallet application asa token, wherein the token is different from an account identifierassigned by the issuer system to the payment device.

Clause 5: The method of any of clauses 1-4, wherein the first rewardsinquiry comprises the token and the second rewards inquiry comprises theaccount identifier, wherein generating the second rewards inquirycomprises replacing the token of the first rewards inquiry with theaccount identifier to form the second rewards inquiry.

Clause 6: The method of any of clauses 1-5, further comprisingreceiving, in the electronic wallet application of the user device, theat least one virtual payment device from a transaction service providersystem associated with the at least one virtual payment device beforestoring the at least one virtual payment device in the electronic walletapplication of the user device.

Clause 7: The method of any of clauses 1-6, wherein the issuer systemcredits an account of the user with the at least the portion of therewards amount to be applied to the debit or credit transaction duringsettlement of the debit or credit transaction.

Clause 8: A system for processing a transaction initiated using anelectronic wallet application, comprising at least one processorprogrammed or configured to: store, in an electronic wallet application,at least one virtual payment device associated with a payment deviceissued to the user by an issuer system, the at least one virtual paymentdevice configured to initiate at least one of a debit and credittransaction; communicate, by the electronic wallet application, arewards inquiry to an issuer system of the issuer; receive, by theelectronic wallet application, a rewards inquiry response from theissuer system, the rewards inquiry response containing a rewards amountassociated with the at least one virtual payment device; display, in theelectronic wallet application, the rewards amount associated with the atleast one virtual payment device; initiate, by the electronic walletapplication, a debit or credit transaction for a transaction amount witha merchant system using the at least one virtual payment device;communicate, by the electronic wallet application, a redemption requestto the issuer system, wherein the redemption request specifies at leasta portion of the rewards amount to be applied to the debit or credittransaction; and receive, by the electronic wallet application, aredemption response comprising an updated rewards amount from the issuersystem, wherein the updated rewards amount comprises a differencebetween the rewards amount and the at least the portion of the rewardsamount applied toward the debit or credit transaction.

Clause 9: The system of clause 8, wherein the at least one processor isfurther programmed or configured to: receive, by the electronic walletapplication, an input indicating that the debit or credit transaction isto be processed using at least a portion of the rewards amount.

Clause 10: The system of clause 8 or clause 9, wherein communicating therewards inquiry to the issuer system comprises the at least oneprocessor: communicating, by the electronic wallet application, a firstrewards inquiry to a transaction service provider system of atransaction service provider associated with the at least one virtualpayment device according to a first application programming interface,wherein the first rewards inquiry causes the transaction serviceprovider system to generate and communicate a second rewards inquiry tothe issuer system according to a second application programminginterface.

Clause 11: The system of any of clauses 8-10, wherein the at least onevirtual payment device is stored in the electronic wallet application asa token, wherein the token is different from an account identifierassigned by the issuer system to the payment device.

Clause 12: The system of any of clauses 8-11, wherein the first rewardsinquiry comprises the token and the second rewards inquiry comprises theaccount identifier, wherein generating the second rewards inquirycomprises replacing the token of the first rewards inquiry with theaccount identifier to form the second rewards inquiry.

Clause 13: The system of any of clauses 8-12, wherein the at least oneprocessor is further programmed or configured to receive, in theelectronic wallet application, the at least one virtual payment devicefrom a transaction service provider system associated with the at leastone virtual payment device before storing the at least one virtualpayment device in the electronic wallet application.

Clause 14: The system of any of clauses 8-13, wherein the redemptionrequest causes the issuer system to credit an account of the user withthe at least the portion of the rewards amount to be applied to thedebit or credit transaction during settlement of the debit or credittransaction.

Clause 15: A computer program product for processing a transactioninitiated using an electronic wallet application, the computer programproduct comprising at least one non-transitory computer-readable mediumincluding one or more instructions that, when executed by at least oneprocessor, cause the at least one processor to: store, in an electronicwallet application, at least one virtual payment device associated witha payment device issued to a user by an issuer system, the at least onevirtual payment device configured to initiate at least one of a debitand credit transaction; communicate, by the electronic walletapplication, a rewards inquiry to an issuer system of the issuer;receive, by the electronic wallet application, a rewards inquiryresponse from the issuer system, the rewards inquiry response containinga rewards amount associated with the at least one virtual paymentdevice; display, in the electronic wallet application, the rewardsamount associated with the at least one virtual payment device;initiate, by the electronic wallet application, a debit or credittransaction for a transaction amount with a merchant system using the atleast one virtual payment device; communicate, by the electronic walletapplication, a redemption request to the issuer system, wherein theredemption request specifies at least a portion of the rewards amount tobe applied to the debit or credit transaction; and receive, by theelectronic wallet application, a redemption response comprising anupdated rewards amount from the issuer system, wherein the updatedrewards amount comprises a difference between the rewards amount and theat least the portion of the rewards amount applied toward the debit orcredit transaction.

Clause 16: The computer program product of clause 15, wherein the one ormore instructions further cause the at least one processor to: receive,by the electronic wallet application, an input indicating that the debitor credit transaction is to be processed using at least a portion of therewards amount.

Clause 17: The computer program product of clause 15 or clause 16,wherein communicating the rewards inquiry to the issuer system comprisesthe at least one processor: communicating, by the electronic walletapplication, a first rewards inquiry to a transaction service providersystem of a transaction service provider associated with the at leastone virtual payment device according to a first application programminginterface, wherein the first rewards inquiry causes the transactionservice provider system to generate and communicate a second rewardsinquiry to the issuer system according to a second applicationprogramming interface.

Clause 18: The computer program product of any of clauses 15-17, whereinthe at least one virtual payment device is stored in the electronicwallet application as a token, wherein the token is different from anaccount identifier assigned by the issuer system to the payment device.

Clause 19: The computer program product of any of clauses 15-18, whereinthe first rewards inquiry comprises the token and the second rewardsinquiry comprises the account identifier, wherein generating the secondrewards inquiry comprises replacing the token of the first rewardsinquiry with the account identifier to form the second rewards inquiry.

Clause 20: The computer program product of any of clauses 15-19, whereinthe one or more instructions further cause the at least one processor toreceive, in the electronic wallet application, the at least one virtualpayment device from a transaction service provider system associatedwith the at least one virtual payment device before storing the at leastone virtual payment device in the electronic wallet application.

Clause 21: The computer program product of any of clauses 15-20, whereinthe redemption request causes the issuer system to credit an account ofthe user with the at least the portion of the rewards amount to beapplied to the debit or credit transaction during settlement of thedebit or credit transaction.

These and other features and characteristics of the present disclosure,as well as the methods of operation and functions of the relatedelements of structures and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the disclosure. Asused in the specification and the claims, the singular form of “a,”“an,” and “the” include plural referents unless the context clearlydictates otherwise. Further, the phrase “based on” is intended to mean“based at least partially on” unless explicitly stated otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional advantages and details of the disclosure are explained ingreater detail below with reference to the non-limiting exemplaryembodiments that are illustrated in the accompanying schematic figures,in which:

FIG. 1 shows a schematic view of a system for processing a transactioninitiated using an electronic wallet application, according to somenon-limiting embodiments or aspects;

FIG. 2 shows a schematic of a graphical user interface for adding apayment device to an electronic wallet application according to somenon-limiting embodiments or aspects;

FIG. 3 shows a schematic view of an enrollment environment for adding apayment device to an electronic wallet application, according to somenon-limiting embodiments or aspects;

FIG. 4 shows a schematic of a graphical user interface for displayingthe payment devices stored in an electronic wallet application,according to some non-limiting embodiments or aspects;

FIG. 5 shows a schematic view of a rewards management system, accordingto some non-limiting embodiments or aspects;

FIG. 6 shows a schematic of a graphical user interface for displayingvirtual payment device information in an electronic wallet application,according to some non-limiting embodiments or aspects;

FIG. 7 shows a schematic of a graphical user interface for prompting auser to indicate whether rewards amount is to be redeemed, according tosome non-limiting embodiments or aspects;

FIG. 8 shows a schematic of a graphical user interface for displayingupdated payment device information in an electronic wallet application,according to some non-limiting embodiments or aspects;

FIG. 9 shows a step diagram of a method for processing a transactioninitiated using an electronic wallet application, according to somenon-limiting embodiments or aspects;

FIG. 10 shows a process flow diagram of a method for processing atransaction initiated using an electronic wallet application, accordingto some non-limiting embodiments or aspects; and

FIG. 11 shows a diagram of a non-limiting embodiment of components ofone or more devices of the system of FIGS. 1, 3, and 5 .

DETAILED DESCRIPTION

For purposes of the description hereinafter, the terms “end,” “upper,”“lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,”“lateral,” “longitudinal,” and derivatives thereof shall relate to thedisclosure as it is oriented in the drawing figures. However, it is tobe understood that the disclosure may assume various alternativevariations and step sequences, except where expressly specified to thecontrary. It is also to be understood that the specific devices andprocesses illustrated in the attached drawings, and described in thefollowing specification, are simply exemplary embodiments or aspects ofthe disclosure. Hence, specific dimensions and other physicalcharacteristics related to the embodiments or aspects disclosed hereinare not to be considered as limiting.

As used herein, the term “account identifier” may include one or moretypes of identifiers associated with a user account (e.g., a PAN, aprimary account number, a card number, a payment card number, a token,and/or the like). In some non-limiting embodiments, an issuerinstitution may provide an account identifier (e.g., a PAN, a token,and/or the like) to a user that uniquely identifies one or more accountsassociated with that user. The account identifier may be embodied on aphysical financial instrument (e.g., a portable financial instrument, apayment card, a credit card, a debit card, and/or the like) and/or maybe electronic information communicated to the user that the user may usefor electronic payments. In some non-limiting embodiments, the accountidentifier may be an original account identifier, where the originalaccount identifier was provided to a user at the creation of the accountassociated with the account identifier. In some non-limitingembodiments, the account identifier may be an account identifier (e.g.,a supplemental account identifier) that is provided to a user after theoriginal account identifier was provided to the user. For example, ifthe original account identifier is forgotten, stolen, and/or the like, asupplemental account identifier may be provided to the user. In somenon-limiting embodiments, an account identifier may be directly orindirectly associated with an issuer institution such that an accountidentifier may be a token that maps to a PAN or other type ofidentifier. Account identifiers may be alphanumeric, any combination ofcharacters and/or symbols, and/or the like. An issuer institution may beassociated with a bank identification number (BIN) that uniquelyidentifies the issuer institution.

As used herein, the term “acquirer” may refer to an entity licensed bythe transaction service provider and approved by the transaction serviceprovider to originate transactions (e.g., payment transactions) using apayment device associated with the transaction service provider. As usedherein, the term “acquirer system” may also refer to one or morecomputer systems, computer devices, and/or the like operated by or onbehalf of an acquirer. The transactions the acquirer may originate mayinclude payment transactions (e.g., purchases, original credittransactions (OCTs), account funding transactions (AFTs), and/or thelike). In some non-limiting embodiments, the acquirer may be authorizedby the transaction service provider to assign merchant or serviceproviders to originate transactions using a payment device of thetransaction service provider. The acquirer may contract with paymentfacilitators to enable the payment facilitators to sponsor merchants.The acquirer may monitor compliance of the payment facilitators inaccordance with regulations of the transaction service provider. Theacquirer may conduct due diligence of the payment facilitators andensure that proper due diligence occurs before signing a sponsoredmerchant. The acquirer may be liable for all transaction serviceprovider programs that the acquirer operates or sponsors. The acquirermay be responsible for the acts of the acquirer's payment facilitators,merchants that are sponsored by an acquirer's payment facilitators,and/or the like. In some non-limiting embodiments, an acquirer may be afinancial institution, such as a bank.

As used herein, the term “application programming interface” (API) mayrefer to computer code that allows communication between differentsystems or (hardware and/or software) components of systems. Forexample, an API may include function calls, functions, subroutines,communication protocols, fields, and/or the like usable and/oraccessible by other systems or other (hardware and/or software)components of systems.

As used herein, the terms “communication” and “communicate” may refer tothe reception, receipt, transmission, transfer, provision, and/or thelike of information (e.g., data, signals, messages, instructions,commands, and/or the like). For one unit (e.g., a device, a system, acomponent of a device or system, combinations thereof, and/or the like)to be in communication with another unit means that the one unit is ableto directly or indirectly receive information from and/or transmitinformation to the other unit. This may refer to a direct or indirectconnection (e.g., a direct communication connection, an indirectcommunication connection, and/or the like) that is wired and/or wirelessin nature. Additionally, two units may be in communication with eachother even though the information transmitted may be modified,processed, relayed, and/or routed between the first and second unit. Forexample, a first unit may be in communication with a second unit eventhough the first unit passively receives information and does notactively transmit information to the second unit. As another example, afirst unit may be in communication with a second unit if at least oneintermediary unit (e.g., a third unit located between the first unit andthe second unit) processes information received from the first unit andcommunicates the processed information to the second unit. In somenon-limiting embodiments, a message may refer to a network packet (e.g.,a data packet and/or the like) that includes data. It will beappreciated that numerous other arrangements are possible.

As used herein, the terms “client” and “client device” may refer to oneor more client-side devices or systems (e.g., remote from a transactionservice provider) used to initiate or facilitate a transaction (e.g., apayment transaction). As an example, a “client device” may refer to oneor more POS devices used by a merchant, one or more acquirer hostcomputers used by an acquirer, one or more mobile devices used by auser, and/or the like. In some non-limiting embodiments, a client devicemay be an electronic device configured to communicate with one or morenetworks and initiate or facilitate transactions. For example, a clientdevice may include one or more computers, portable computers, laptopcomputers, tablet computers, mobile devices, cellular phones, wearabledevices (e.g., watches, glasses, lenses, clothing, and/or the like),PDAs, and/or the like. Moreover, a “client” may also refer to an entity(e.g., a merchant, an acquirer, and/or the like) that owns, utilizes,and/or operates a client device for initiating transactions (e.g., forinitiating transactions with a transaction service provider).

As used herein, the terms “electronic wallet,” “electronic wallet mobileapplication,” and “digital wallet” may refer to one or more electronicdevices and/or one or more software applications configured to initiateand/or conduct transactions (e.g., payment transactions, electronicpayment transactions, and/or the like). For example, an electronicwallet may include a user device (e.g., a mobile device) executing anapplication program and server-side software and/or databases formaintaining and providing transaction data to the user device. As usedherein, the term “electronic wallet provider” may include an entity thatprovides and/or maintains an electronic wallet and/or an electronicwallet mobile application for a user (e.g., a customer). Examples of anelectronic wallet provider include, but are not limited to, GoogleWallet™, Android Pay®, Apple Pay®, and Samsung Pay®. In somenon-limiting examples, a financial institution (e.g., an issuerinstitution) may be an electronic wallet provider. As used herein, theterm “electronic wallet provider system” may refer to one or morecomputer systems, computer devices, servers, groups of servers, and/orthe like operated by or on behalf of an electronic wallet provider.

As used herein, the terms “issuer institution,” “issuer,” or “issuerbank” may refer to one or more entities that provide accounts tocustomers for conducting transactions (e.g., payment transactions), suchas initiating credit and/or debit payments. For example, an issuerinstitution may provide an account identifier, such as a personalaccount number (PAN), to a customer that uniquely identifies one or moreaccounts associated with that customer. The account identifier may beembodied on a payment device, such as a physical financial instrument,e.g., a payment card, and/or may be electronic and used for electronicpayments. The terms “issuer institution” and “issuer institution system”may also refer to one or more computer systems operated by or on behalfof an issuer institution, such as a server computer executing one ormore software applications. For example, an issuer institution systemmay include one or more authorization servers for authorizing atransaction.

As used herein, the term “merchant” may refer to an individual or entitythat provides goods and/or services, or access to goods and/or services,to customers based on a transaction, such as a payment transaction. Asused herein, the terms “merchant” or “merchant system” may also refer toone or more computer systems operated by or on behalf of a merchant,such as a server computer executing one or more software applications.As used herein, the term “point-of-sale (POS) system,” may refer to oneor more computers and/or peripheral devices used by a merchant to engagein payment transactions with customers, including one or more cardreaders, near-field communication (NFC) receivers, RFID receivers,and/or other contactless transceivers or receivers, contact-basedreceivers, payment terminals, computers, servers, input devices, and/orother like devices that can be used to initiate a payment transaction.

As used herein, the term “payment device” may refer to a payment card(e.g., a credit or debit card), a gift card, a smartcard, smart media, apayroll card, a healthcare card, a wristband, a machine-readable mediumcontaining account information, a keychain device or fob, an RFIDtransponder, a retailer discount or loyalty card, a cellular phone, anelectronic wallet mobile application, a personal digital assistant(PDA), a pager, a security card, a computer, an access card, a wirelessterminal, a transponder, and/or the like. In some non-limitingembodiments, the payment device may include volatile or non-volatilememory to store information (e.g., an account identifier, a name of theaccount holder, and/or the like).

As used herein, the terms “payment token” or “token” may refer to anidentifier that is used as a substitute or replacement identifier for anaccount identifier, such as a PAN. Tokens may be associated with a PANor other account identifiers in one or more data structures (e.g., oneor more databases and/or the like) such that they can be used to conducta transaction (e.g., a payment transaction) without directly using theaccount identifier, such as a PAN. In some examples, an accountidentifier, such as a PAN, may be associated with a plurality of tokensfor different individuals, different uses, and/or different purposes.For example, a payment token may include a series of numeric and/oralphanumeric characters that may be used as a substitute for an originalaccount identifier. For example, a payment token “4900 0000 0000 0001”may be used in place of a PAN “4147 0900 0000 1234.” In somenon-limiting embodiments, a payment token may be “format preserving” andmay have a numeric format that conforms to the account identifiers usedin existing payment processing networks (e.g., ISO 8583 financialtransaction message format). In some non-limiting embodiments, a paymenttoken may be used in place of a PAN to initiate, authorize, settle, orresolve a payment transaction or represent the original credential inother systems where the original credential would typically be provided.In some non-limiting embodiments, a token value may be generated suchthat the recovery of the original PAN or other account identifier fromthe token value may not be computationally derived (e.g., with a one-wayhash or other cryptographic function). Further, in some non-limitingembodiments, the token format may be configured to allow the entityreceiving the payment token to identify it as a payment token andrecognize the entity that issued the token.

As used herein, the term “server” may refer to one or more computingdevices (e.g., processors, storage devices, similar computer components,and/or the like) that communicate with client devices and/or othercomputing devices over a network (e.g., a public network, the Internet,a private network, and/or the like) and, in some examples, facilitatecommunication among other servers and/or client devices. It will beappreciated that various other arrangements are possible. As usedherein, the term “system” may refer to one or more computing devices orcombinations of computing devices (e.g., processors, servers, clientdevices, software applications, components of such, and/or the like).Reference to “a device,” “a server,” “a processor,” and/or the like, asused herein, may refer to a previously-recited device, server, orprocessor that is recited as performing a previous step or function, adifferent server or processor, and/or a combination of servers and/orprocessors. For example, as used in the specification and the claims, afirst server or a first processor that is recited as performing a firststep or a first function may refer to the same or different server orthe same or different processor recited as performing a second step or asecond function.

As used herein, the term a “token service provider” may refer to anentity including one or more server computers in a token service systemthat generates, processes and maintains payment tokens. For example, thetoken service provider may include or be in communication with a tokenvault where the generated tokens are stored. Additionally oralternatively, the token vault may maintain one-to-one mapping between atoken and a PAN represented by the token. In some non-limitingembodiments, the token service provider may have the ability to setaside licensed BINs as token BINs to issue tokens for the PANs that maybe submitted to the token service provider. In some non-limitingembodiments, various entities of a tokenization ecosystem may assume theroles of the token service provider. For example, payment networks andissuers or their agents may become the token service provider byimplementing the token services according to non-limiting embodiments ofthe presently disclosed subject matter. Additionally or alternatively, atoken service provider may provide reports or data output to reportingtools regarding approved, pending, or declined token requests, includingany assigned token requestor ID. The token service provider may providedata output related to token-based transactions to reporting tools andapplications and present the token and/or PAN as appropriate in thereporting output. In some non-limiting embodiments, the EMVCo standardsorganization may publish specifications defining how tokenized systemsmay operate. For example, such specifications may be informative, butthey are not intended to be limiting upon any of the presently disclosedsubject matter.

As used herein, the term “token vault” may refer to a repository thatmaintains established token-to-PAN mappings. For example, the tokenvault may also maintain other attributes of the token requestor that maybe determined at the time of registration and/or that may be used by thetoken service provider to apply domain restrictions or other controlsduring transaction processing. In some non-limiting embodiments, thetoken vault may be a part of a token service system. For example, thetoken vault may be provided as a part of the token service provider.Additionally or alternatively, the token vault may be a remoterepository accessible by the token service provider. In somenon-limiting embodiments, token vaults, due to the sensitive nature ofthe data mappings that are stored and managed therein, may be protectedby strong underlying physical and logical security. Additionally oralternatively, a token vault may be operated by any suitable entity,including a payment network, an issuer, clearing houses, other financialinstitutions, transaction service providers, and/or the like.

As used herein, the term “transaction service provider” may refer to anentity that receives transaction authorization requests from merchantsor other entities and provides guarantees of payment, in some casesthrough an agreement between the transaction service provider and theissuer institution. In some non-limiting embodiments, a transactionservice provider may include a credit card company, a debit cardcompany, and/or the like. As used herein, the term “transaction serviceprovider system” may also refer to one or more computer systems operatedby or on behalf of a transaction service provider, such as a transactionprocessing server executing one or more software applications. Atransaction processing server may include one or more processors and, insome non-limiting embodiments, may be operated by or on behalf of atransaction service provider.

As used herein, the term “user interface” or “graphical user interface”refers to a generated display, such as one or more graphical userinterfaces (GUIs) with which a user may interact, either directly orindirectly (e.g., through a keyboard, mouse, etc.).

Non-limiting embodiments or aspects of the present disclosure aredirected to a method, system, and computer program product forprocessing a transaction initiated using an electronic walletapplication. Non-limiting embodiments or aspects enable a user toefficiently view and redeem rewards points associated with each paymentdevice stored in the electronic wallet. This feature is enabled by theunique system arrangement in which issuers of the payment deviceintegrate with the transaction service providers and the electronicwallet providers via application programming interfaces, as opposed tothe issuer integrating with individual merchants, and a non-conventionalflow between the electronic wallet, transaction service provider, andissuer(s). Non-limiting embodiments or aspects allow the user to viewrewards information associated with the payment device in the electronicwallet. Further, during processing of a payment transaction initiatedusing a payment device stored in the electronic wallet, the user is ableto redeem the rewards associated with that payment device by indicatingto the electronic wallet that at least a portion of the rewards amountis to be redeemed. Practically, this allows the user to redeem rewardspoints associated with the payment device being used to initiate thetransaction, regardless of the merchant with whom the transaction isbeing initiated. Non-limiting embodiments or aspects provide the userwith enhanced flexibility for redeeming earned rewards, allowing thoserewards to be used more easily and preventing waste (expiration) ofearned rewards.

Referring to FIG. 1 , a system 10 for processing a transaction initiatedusing an electronic wallet application according to some non-limitingembodiments or aspects is shown. The system 10 may include a user device12 of a user (e.g., a consumer engaging in payment transactions with amerchant). The user device 12 may be a client device, such as asmartphone, a tablet computer, and the like. The user device 12 mayinclude an electronic wallet (e-wallet) application 14 downloaded and/orinstalled on the user device 12. The e-wallet application 14 may allowusers to store virtual payment devices associated with physical paymentdevices (e.g., credit or debit cards) in the e-wallet application 14,such that the e-wallet application 14 allows the user to initiate apayment transaction using the user device 12 by using one of the virtualpayment devices stored in the e-wallet application 14 to initiate thepayment transaction.

With continued reference to FIG. 1 , the user device 12 containing thee-wallet application 14 may initiate a payment transaction using thee-wallet application 14, and that payment transaction may be processed(e.g., authorized cleared, settled) by the user device 12 via thee-wallet application 14 communicating with an electronic paymentprocessing network 16 and a rewards management system 18. The electronicpayment processing network 16 may include a merchant system 20 incommunication with the e-wallet application 14. The electronic paymentprocessing network 16 may include a transaction service provider system22 in communication with the merchant system 20 (e.g., directly or viaan acquirer system (not pictured)). The electronic payment processingnetwork 16 may include the transaction service provider system 22 incommunication with a plurality of issuer systems 24 a-24 c. The merchantsystem 20 may be operated by or on behalf of the merchant engaging inthe payment transaction with the user. The transaction service providersystem 22 may be operated by or on behalf of the transaction serviceprovider associated with the payment device associated with virtualpayment device being used to initiate the payment transaction. Theissuer systems 24 a-24 c may be operated by or on behalf of issuers ofpayment devices, and the transaction service provider system 22 maycommunicate with the issuer system 24 a-24 c which issued the paymentdevice associated with virtual payment device used to initiate thepayment transaction, in order to process the payment transaction.

The rewards management system 18 may include a transaction serviceprovider (TSP) rewards system 26 in communication with the e-walletapplication 14. The TSP rewards system 26 may be operated by or onbehalf of a transaction service provider. The TSP rewards system 26 mayrefer to one or more computer systems operated by or on behalf of atransaction service provider, such as a rewards processing serverexecuting one or more software applications. A rewards processing servermay include one or more processors. The TSP rewards system 26 may be thesame system as the transaction service provider system 22, or the TSPrewards system 26 may a separate system from the transaction serviceprovider system 22.

The TSP rewards system 26 may be in communication with issuer rewardssystems 28 a-28 c. The issuer rewards systems 28 a-28 c may be operatedby or on behalf of issuers of payment devices, and the TSP rewardssystem 26 may communicate with the issuer rewards system 28 a-28 c whichissued the payment device associated with virtual payment device used toinitiate the payment transaction in order to process the later-describedrewards redemption process. The issuer rewards system 28 a-28 c mayrefer to one or more computer systems operated by or on behalf of anissuer, such as a rewards processing server executing one or moresoftware applications. The issuer rewards system 28 a-28 c may be thesame system as the corresponding issuer system 24 a-24 c, or the issuerrewards system 28 a-28 c may a separate system from the correspondingissuer system 24 a-24 c.

Referring to FIGS. 2 and 3 , a user may store at least one virtualpayment device associated with a payment device in the e-walletapplication 14 to allow the user to initiate payment transactions usingtheir user device 12 using a virtual payment device stored in thee-wallet application 14.

FIG. 2 shows a graphical user interface 30 for adding a payment deviceto an e-wallet application 14 by storing a virtual payment device,according to some non-limiting embodiments or aspects. By adding thepayment device to the e-wallet application 14, the payment device isstored in the e-wallet application 14 as the virtual payment device,which includes certain account information relevant for initiating andprocessing a payment transaction. Such account information may include,but is not limited to, one or more of the following: cardholder name,PAN (or token associated therewith), expiration date, card verificationvalue (cvv) code, and/or the like. The graphical user interface 30 mayinclude input fields to allow the user to enter the relevant accountinformation into the user device 12 to store the payment device as avirtual payment device in the e-wallet application 14. After enteringthe relevant account information into the graphical user interface 30,the user may submit the account information to cause the virtual paymentdevice to be stored in the e-wallet application 14. It will beappreciated that any arrangement of the graphical user interface 30 maybe used to enter and store virtual payment devices, such as usinganother arrangement of input fields and selectable options. The user mayenter a single payment device or multiple payment devices into thee-wallet application 14.

Referring to FIG. 3 , an enrollment environment 40 may include thee-wallet application 14 receiving at least one virtual payment devicefrom an enrollment system 42. The enrollment system 42 may refer to oneor more computer systems operated by or on behalf of a transactionservice provider (e.g., the same as or part of the transaction serviceprovider system 22, the TSP rewards system 26, and/or the like), issuer(e.g., the same as or part of one of the issuer systems 24 a-24 c,issuer rewards systems 28 a-28 c, and/or the like), or other entity,such as a processing server executing one or more software applications.The enrollment system 42 may be operated by or on behalf of thetransaction service provider associated with the virtual payment devicebeing received by the e-wallet application 14. In response to receivingthe virtual payment device from the enrollment system 42, the e-walletapplication 14 may store the virtual payment device. Thus, in additionto or in lieu of the user entering account information associated with apayment device as described in connection with FIG. 2 , the enrollmentsystem 42 may communicate the virtual payment device to the e-walletapplication 14 to be stored. In some non-limiting embodiments oraspects, virtual payment devices may be stored in the e-walletapplication 14 by a combination of the user entering account informationassociated with a payment device to store a virtual payment device andthe e-wallet application 14 receiving at least one virtual paymentdevice from the enrollment system 42. In some non-limiting embodimentsor aspects, the user may enter a first payment device into the userdevice 12 to be stored as a virtual payment device in the e-walletapplication 14, and the e-wallet application 14 may communicate with theenrollment system 42 to confirm the virtual payment device (e.g., thatthe virtual payment device is a valid or active payment device issued tothe user) and/or to determine other payment devices associated with theuser, such that the user's other payment devices may be stored asvirtual payment devices in the e-wallet application 14. The enrollmentsystem 42 may communicate these determined additional virtual paymentdevices to the e-wallet application 14 for storage. The enrollmentsystem 42 may communicate with a cardholder database 44 to determineadditional payment devices associated with the user. The cardholderdatabase 44 may contain information associating cardholders with variouspayment devices issued thereto.

With continued reference to FIG. 3 , in some non-limiting embodiments oraspects, the virtual payment devices may be stored in the e-walletapplication 14 as a token different from the account identifier (e.g.,PAN) assigned by the issuer system to the payment device. In somenon-limiting embodiments or aspects, the e-wallet application 14 may notstore the account identifier assigned by the issuer system to thepayment device for security purposes.

In some non-limiting embodiments or aspects, the e-wallet application 14may communicate the user's account information and/or a virtual paymentdevice (including the PAN number thereof) to the enrollment system 42for tokenization. The enrollment system 42 may communicate the accountinformation and/or the virtual payment device to a tokenization system46, which may generate a token to be associated with the virtual paymentdevice. The generated token may be communicated to the enrollment system42. The tokenization system 46 may include a token vault for storing andmapping issued tokens with their associated virtual payment devices. Theenrollment system 42 may communicate the generated token to the e-walletapplication 14 for storage, in addition to or instead of storing thePAN, and/or other account information.

In some non-limiting embodiments or aspects, the enrollment system 42may determine payment devices associated with the user by communicatingwith the cardholder database 44. The enrollment system 42 maycommunicate the determined payment devices to the tokenization system46, which may generate a token to be associated with each virtualpayment device. The generated tokens may be communicated to theenrollment system 42, which may communicate the tokens to the e-walletapplication 14 for storage as the virtual payment devices. Thetokenization system 46 may store the generated tokens in the tokenvault.

Referring to FIG. 4 , a graphical user interface 48 displaying allvirtual payment devices stored on the user device 12 in the e-walletapplication 14 is shown according to some non-limiting embodiments oraspects. The graphical user interface 48 may list all virtual paymentdevices stored in the e-wallet application 14 and available to the userto initiate a payment transaction using the user device 12. The user mayinteract with the graphical user interface 48 to select at least one ofthe displayed, listed virtual payment devices in order to allow the userto view more information associated with the selected virtual paymentdevice or to allow the user to initiate a payment transaction using theselected virtual payment device. Any number of virtual payment devicesmay be stored in the e-wallet application 14 and displayed on thegraphical user interface 48, and the graphical user interface 48 mayinclude any suitable arrangement of the virtual payment devices.

Referring to FIG. 5 , the rewards management system 18 according to somenon-limiting embodiments or aspects is shown. The rewards managementsystem 26 may process rewards inquiries. A rewards inquiry may include arequest from the user device 12 via the e-wallet application 14requesting rewards information associated with at least one virtualpayment device stored in the e-wallet application 14. The rewardsinquiry may be initiated by the user selecting a virtual payment devicein the e-wallet application 14 (such as via the graphical user interface48 shown in FIG. 4 ). The user device 14 may communicate a first rewardsinquiry associated with a virtual payment device to the TSP rewardssystem 26. The first rewards inquiry may be communicated from userdevice 12 via the e-wallet application 14 to the TSP rewards system 26according to a first application programming interface as describedherein. The first rewards inquiry may cause the TPS rewards system 26 togenerate and communicate a second rewards inquiry to the relevant issuerrewards system 28 a-28 c (e.g., the issuer rewards system of the issuerthat issued the payment device associated with the virtual paymentdevice) according to a second application programming interface, asdescribed herein. The first rewards inquiry may include accountinformation, the PAN, the token, and/or the like associated with thevirtual payment device.

In response to receiving the first rewards inquiry, the TSP rewardssystem 26 may determine the issuer associated with the virtual paymentdevice (e.g., the issuer who issued the payment device associated withthe virtual payment device to the user). This determination may be madeby the TSP rewards system 26 communicating with the cardholder database44, which may include information associating users with various paymentdevices and the issuers issuing those payment devices. In response todetermining the issuer associated with the virtual payment device, theTSP rewards system 26 may communicate a second rewards inquiry includingthe first rewards inquiry, at least in part, to the relevant issuerrewards system 28 a-28 c. The relevant rewards system 28 a-28 c mayrespond by communicating a rewards inquiry response to the TSP rewardssystem 26, the rewards inquiry response including rewards informationassociated with the virtual payment device associated with the firstrewards inquiry. The rewards information may include, but is not limitedto, at least one of a rewards amount (e.g., a monetary currency, arewards currency (e.g., rewards points, airline miles, and the like), acryptocurrency, or other type of currency), a conversion amount ofrewards (e.g., from a rewards currency to a monetary currency, betweenrewards currencies, or between monetary currencies, or any other type ofcurrency exchange, including currency exchanges includingcryptocurrencies), an expiration date associated with the rewardsamount, and the like. The TSP rewards system 26 may communicate therewards inquiry response including the rewards information to thee-wallet application 14 of the user device 12. The e-wallet application14 may display the rewards amount and/or other rewards informationassociated with virtual payment device.

With continued reference to FIG. 5 , in some non-limiting embodiments oraspects, the first rewards inquiry from the e-wallet application 14 tothe TSP rewards system 26 may include the token associated with thevirtual payment device associated with the rewards inquiry (e.g.,because the e-wallet application 14 has not stored the PAN associatedwith the payment device and/or stored the token in lieu of the PAN). Inresponse to receiving the token in the first rewards inquiry, the TSPrewards system 26 may communicate with the tokenization system 46 toreceive the account identifier (stored in the token vault and associatedwith the token) assigned by the issuer (such as the PAN) associated withthe virtual payment device based on the account identifier. The TSPrewards system 26 may communicate with the cardholder database 44 todetermine the issuer of the virtual payment device. The TSP rewardssystem 26 may communicate the second rewards inquiry, which may includethe account identifier assigned by the issuer in addition to or in lieuof the token to the relevant issuer rewards system 28 a-28 c. The tokenfrom the first rewards inquiry may be replaced by the account identifierassigned by the issuer in the second rewards inquiry.

Referring to FIG. 6 a graphical user interface 50 for displaying virtualpayment device information in an electronic wallet application accordingto some non-limiting embodiments or aspects is shown. The graphical userinterface 50 may display at least some of the rewards informationreceived in response to the rewards inquiry. As shown in FIG. 6 , therewards amount 52 associated with the virtual payment device may bedisplayed, including an amount in monetary currency (e.g., US dollars)corresponding to the rewards amount. As shown in FIG. 6 , an expirationdate 54 associated with the rewards amount 52 may be displayed. Suchinformation may be displayed for each virtual payment device stored inthe e-wallet application 14 based on rewards information received inresponse to a rewards inquiry communicated in association with eachvirtual rewards card. The graphical user interface 50 for displayingvirtual payment device information, including rewards information, mayuse any suitable arrangement for displaying the virtual payment deviceand its associated rewards information.

Referring again to FIG. 1 , the user may initiate a payment transactionwith a merchant using the user device 12 via the e-wallet application14. The payment transaction may include a credit transaction, debittransaction, and/or the like. The payment transaction may be initiatedusing at least one of the virtual payment devices stored in the e-walletapplication 14. The user may initiate the payment transaction via thee-wallet application 14 by communicating with the merchant system 20(e.g., the merchant's point-of-sale (POS) system). For example, userdevice 12 may communicate with a POS system by at least one of one ormore card readers, near-field communication (NFC) receivers, RFIDreceivers, and/or other contactless transceivers or receivers,contact-based receivers, payment terminals, computers, servers, inputdevices, and/or other like devices that can be used to initiate apayment transaction

In response, the merchant system 20 may initiate processing of thepayment transaction by communicating a transaction message (e.g., firstauthorization request) to the transaction service provider system 22(e.g., directly or via an acquirer). The transaction message may includeaccount information associated with the virtual payment device (e.g.,PAN or token associate therewith, cardholder name, expiration date, cvvcode, and/or the like) selected by the user to initiate the paymenttransaction, as well as other information relevant for processing thepayment transaction, e.g., merchant information, transaction amount,goods and/or services purchased, and/or the like. The transactionservice provider system 22 may communicate at least a portion of thetransaction message (e.g., a second authorization request including atleast a portion of the transaction message) to the relevant issuersystem 24 a-24 c (e.g., the issuer system of the issuer which issued thevirtual payment device to the user).

In response to receiving the second authorization request, the issuersystem 24 a-24 c may determine an authorization decision associated withthe payment transaction. The authorization decision may be, but is notlimited to, at least one of: to approve the payment transaction, todecline the payment transaction, and/or the like to approve the paymenttransaction in part and decline the payment transaction in part. Theissuer system 24 a-24 c may communicate an authorization response (e.g.,first authorization response) including the authorization decision tothe transaction service provider system 22. The transaction serviceprovider system 22 may communicate a transaction response (e.g., thefirst authorization response, a second authorization response based onthe first authorization response, and/or the like) including theauthorization decision to the merchant system 20. Additionally, themerchant system 20 may communicate the authorization decision to theuser device 12 (e.g., the e-wallet application 14 thereof).

With continued reference to FIG. 1 , before, during, or after processingor authorization of the payment transaction in the electronic paymentprocessing network 16 as described above, and in response to the userinitiating the payment transaction with a merchant, the user device 12,via the e-wallet application 14, may communicate a redemption requestspecifying that at least a portion of the rewards amount associated withthe virtual payment device used to initiate the payment transaction isto be applied to the payment transaction. The redemption request may becommunicated from the e-wallet application 14 to the rewards managementsystem 18 for processing, such as by communicating the redemptionrequest to the TSP rewards system 26.

Referring to FIG. 7 , FIG. 7 shows a graphical user interface 56 forprompting a user and allowing the user to indicate whether rewardsamount is to be redeemed according to some non-limiting embodiments oraspects. For example, communicating the redemption request may includethe user device 12 receiving an input from the user to indicate that thepayment transaction is to be processed using at least a portion of therewards amount. The user may indicate via a rewards redemption prompt 58on the graphical user interface 56 that a rewards amount associated withthe virtual payment device is to be applied for the payment transactionor is not to be applied to the payment transaction. The user may alsoinput into the user device 12 a rewards amount associated with thevirtual payment device to be applied to the payment transaction. Forexample, the user may indicate that an entire rewards amount is to beapplied or only a specified portion thereof is to be applied. Thegraphical user interface 56 for prompting a user and allowing the userto indicate whether rewards amount is to be redeemed may use anysuitable arrangement.

Referring again to FIG. 1 , in response to the TSP rewards system 26receiving the redemption request, the TSP rewards system 26 maycommunicate the redemption request to the issuer rewards system 28 a-28c associated with the issuer associated with the virtual payment deviceused to initiate the payment transaction. The issuer rewards system 28a-28 c may process the redemption request by applying the rewards amountto the payment transaction. In some non-limiting embodiments or aspects,applying the rewards amount to the payment transaction may include therewards amount being applied to the transaction amount associated withthe payment transaction during processing of the payment transaction.Additionally or alternatively, the rewards amount may be applied to thepayment transaction prior to authorization of the payment transaction bythe corresponding issuer system 24 a-24 c, e.g., to reduce thetransaction amount being authorized by the rewards amount. In somenon-limiting embodiments or aspects, the rewards amount may be appliedto the payment transaction during settlement of the payment transaction.For example, the issuer may give the user statement credit for therewards amount. It will be appreciated that the rewards amount may beapplied at other stages during or after processing of the paymenttransaction.

With continued reference to FIG. 1 , the issuer rewards system 28 a-28 cmay communicate a redemption response to the TSP rewards system 26 e.g.,to notify TSP rewards system 26 and/or the user that the rewards amountin the redemption request has been, is being, or will be applied to thepayment transaction. The TSP rewards system 26 may communicate thisredemption response to the e-wallet application 14 on the user device12. The redemption response may further include an updated rewardsamount associated with the virtual payment device used to initiate thepayment transaction. The updated rewards amount may include a differencebetween the rewards amount originally available for the virtual paymentdevice and the portion of the rewards amount applied toward the paymenttransaction.

As shown in FIG. 8 , FIG. 8 shows a graphical user interface 60 fordisplaying updated payment device information in the e-walletapplication 14 according to some non-limiting embodiments or aspects.The user device 12 may show the updated rewards amount in the e-walletapplication 14. The updated payment device information may include anupdated rewards amount 62, such as in rewards points and/or incorresponding monetary currency. The updated payment device informationmay also include updated expiration date information 64 indicating atleast one date on which at least a portion of the updated rewards amount62 expires. The graphical user interface for displaying updated paymentdevice information may use any suitable arrangement for displayingupdated payment device information.

Referring to FIG. 9 , a method 70 for processing a transaction initiatedusing an e-wallet application 14 (see FIG. 1 ) according to somenon-limiting embodiments or aspects is shown. Steps of the method 70 maybe performed by the components shown in FIG. 1 .

At step 72, the e-wallet application 14 may cause the user device 12 tostore the at least one virtual payment device associated with a paymentdevice issued to the user by the issuer system 24 a-24 c (see FIG. 1 ).The at least one virtual payment device may be configured to initiate atleast one of a debit transaction, a credit transaction, and/or the like.The virtual payment device may be stored in the e-wallet application 14as a token different from the account identifier assigned by the issuerto the payment device. The virtual payment device may be received fromthe enrollment system 42, which may be stored in the e-walletapplication 14.

At step 74, the e-wallet application 14 may cause the user device 12 tocommunicate the rewards inquiry to the issuer rewards system 28 a-28 cof the issuer (e.g., through the TSP rewards system 26 (see FIG. 1 )).Communicating the rewards inquiry may include communicating a firstrewards inquiry to the TSP rewards system 26 associated with the atleast one virtual payment device according to a first applicationprogramming interface, where the first rewards inquiry causes the TSPrewards system 26 to generate and communicate a second rewards inquiryto the issuer rewards system 28 a-28 c according to a second applicationprogramming interface. The first rewards inquiry may include the token,and the second rewards inquiry may include the account identifier, wheregenerating the second rewards inquiry may include replacing the token ofthe first rewards inquiry with the account identifier to form the secondrewards inquiry.

At step 76, the e-wallet application 14 may cause the user device 12 toreceive the rewards inquiry response from the issuer rewards system 28a-28 c. The rewards inquiry response may contain a rewards amountassociated with the at least one virtual payment device.

At step 78, the e-wallet application 14 may cause the user device 12 todisplay the rewards amount associated with the at least one virtualpayment device.

At step 80, the e-wallet application 14 may cause the user device 12 toinitiate the debit or credit (payment transaction) transaction for atransaction amount with the merchant system 20 (see FIG. 1 ) using theat least one virtual payment device.

At step 82, the e-wallet application 14 may cause the user device 12 tocommunicate the redemption request to the issuer rewards system 28 a-28c. The redemption request may specify at least a portion of the rewardsamount to be applied to the debit or credit transaction by a usercommunicating an input indicating that the debit transaction, credittransaction, and/or the like is to be processed using at least portionof the rewards amount.

At step 84, the e-wallet application 14 may cause the user device 12 toreceive a redemption response comprising an updated rewards amount fromthe issuer rewards system 28 a-28 c. The updated rewards amount mayinclude a difference between the rewards amount and the at least theportion of the rewards amount applied toward the debit or credittransaction. The issuer system may credit an account of the user with atleast a portion of the rewards amount to be applied to the debit orcredit transaction during settlement of the payment transaction.

In some non-limiting embodiment or aspects, a computer program productfor processing a transaction initiated using an electronic walletapplication includes at least one non-transitory computer readablemedium including program instructions that, when executed by at leastone processor, cause the at least one processor to execute any of thepreviously-described systems and/or methods. For example, the userdevice 12 on which the e-wallet application 14 is downloaded orinstalled may include the at least one processor.

Referring to FIG. 11 , FIG. 11 is a diagram of example components of adevice 100. Device 100 may correspond to one or more devices of thesystems shown in FIGS. 1, 3, and 5 . In some non-limiting embodiments,any of the devices shown in FIGS. 1, 3 , and 5 (e.g., the user device12) may include at least one device 100 and/or at least one component ofdevice 100. As shown in FIG. 11 , device 100 may include bus 102,processor 104, memory 106, storage component 108, input component 110,output component 112, and communication interface 114.

Bus 102 may include a component that permits communication among thecomponents of device 100. In some non-limiting embodiments, processor104 may be implemented in hardware, firmware, or a combination ofhardware and software. For example, processor 104 may include aprocessor (e.g., a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), and/or the like), amicroprocessor, a digital signal processor (DSP), and/or any processingcomponent (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), and/or the like), and/orthe like, which can be programmed to perform a function. Memory 106 mayinclude random access memory (RAM), read only memory (ROM), and/oranother type of dynamic or static storage device (e.g., flash memory,magnetic memory, optical memory, and/or the like) that storesinformation and/or instructions for use by processor 104.

Storage component 108 may store information and/or software related tothe operation and use of device 100. For example, storage component 108may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, and/or the like), a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of computer-readable medium, alongwith a corresponding drive.

Input component 110 may include a component that permits device 100 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, a camera, and/or the like). Additionally or alternatively,input component 110 may include a sensor for sensing information (e.g.,a global positioning system (GPS) component, an accelerometer, agyroscope, an actuator, and/or the like). Output component 112 mayinclude a component that provides output information from device 100(e.g., a display, a speaker, one or more light-emitting diodes (LEDs),and/or the like).

Communication interface 114 may include a transceiver-like component(e.g., a transceiver, a receiver and transmitter that are separate,and/or the like) that enables device 100 to communicate with otherdevices, such as via a wired connection, a wireless connection, or acombination of wired and wireless connections. Communication interface114 may permit device 100 to receive information from another deviceand/or provide information to another device. For example, communicationinterface 114 may include an Ethernet interface, an optical interface, acoaxial interface, an infrared interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, a Wi-Fi®interface, aBluetooth® interface, a Zigbee® interface, a cellular network interface,and/or the like.

Device 100 may perform one or more processes described herein. Device100 may perform these processes based on processor 104 executingsoftware instructions stored by a computer-readable medium, such asmemory 106 and/or storage component 108. A computer-readable medium(e.g., a non-transitory computer-readable medium) is defined herein as anon-transitory memory device. A non-transitory memory device includesmemory space located inside of a single physical storage device ormemory space spread across multiple physical storage devices.

Software instructions may be read into memory 106 and/or storagecomponent 108 from another computer-readable medium or from anotherdevice via communication interface 114. When executed, softwareinstructions stored in memory 106 and/or storage component 108 may causeprocessor 104 to perform one or more processes described herein.Additionally or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, embodiments described herein are notlimited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 11 are providedas an example. In some non-limiting embodiments or aspects, device 100may include additional components, fewer components, differentcomponents, or differently arranged components than those shown in FIG.11 . Additionally or alternatively, a set of components (e.g., one ormore components) of device 100 may perform one or more functionsdescribed as being performed by another set of components of device 100.

The following example is provided to illustrate an embodiment of thesystem, method, and computer program product for processing atransaction initiated using an e-wallet application 14, and is not meantto be limiting.

Referring to FIG. 10 , a method 90 for processing a transactioninitiated using an e-wallet application 14 is shown according to somenon-limiting embodiments or aspects. For example, a user may use a userdevice 12 (e.g., smartphone) having downloaded thereon an e-walletapplication 14 capable of initiating payment transactions.

At step S1, the user device 12 may store a payment device as a virtualpayment device on the e-wallet application 14, e.g., based on the userentering payment device information into the user device 12. The paymentdevice may be associated with a transaction service provider and/or anissuer. For example, the payment device may have been issued to the byan issuer bank.

At step S2, the e-wallet application 14 may communicate with anenrollment system 42 of the transaction service provider to enroll thepayment device with the e-wallet application 14, such as by confirmingthat the payment device is associated with or issued to the user.Additionally or alternatively, the transaction service provider, via theenrollment system 42, may also provide supplemental virtual paymentdevice information associated with the payment device (e.g., a token tostore in lieu of a PAN) and/or provide additional virtual paymentdevices issued to the user to the e-wallet application 14.

At step S3, the e-wallet application 14 may communicate a first rewardsinquiry to a TSP rewards system 26 of the transaction service providerto inquire regarding the available rewards amount associated with thevirtual payment device.

At step S4, the TSP rewards system 26 may communicate a second rewardsinquiry including at least a portion of the first rewards inquiry to theissuer 1 rewards system 28 a associated with the issuer, e.g., upon theTSP rewards system 26 determining the issuer bank associated with thevirtual payment device.

At step S5, the issuer 1 rewards system 28 a may communicate a rewardsinquiry response to the TSP rewards system 26, and the rewards inquiryresponse may include an available rewards amount associated with thevirtual payment device.

At step S6, the TSP rewards system 26 may communicate the rewardsinquiry response, which may include the available rewards amount to thee-wallet application 14. At step S7, the e-wallet application 14 maycause the user device 12 to display the rewards amount associated withthe virtual payment device. For example, referring to FIG. 6 , thevirtual payment device issued to the user has 10,000 rewards points,corresponding to $100 USD, which expire on Jan. 5, 2020.

At step S8, the user may select the virtual payment device to be used toinitiate a payment transaction with a merchant for goods from themerchant by selecting the virtual payment device in the e-walletapplication 14 of the user device 12.

At step S9, the e-wallet application 14 may initiate the paymenttransaction with the merchant by communicating with a merchant system 20of the merchant. For example, the user device 12 on which the e-walletapplication 14 is downloaded may be moved in the vicinity of themerchant system 20 (e.g., a merchant POS device) to enable communicationtherebetween. The e-wallet application 14 may communicate accountinformation associated with the virtual payment device, such that thevirtual payment device is the payment device used to process the paymenttransaction.

At step S10, in response to the e-wallet application 14 initiating apayment transaction with the merchant system 20, the merchant system 20may initiate processing of the payment transaction by communicating atransaction message to the transaction service provider system 22 (e.g.,directly or via an acquirer). The transaction service provider system 22may be operated by or on behalf of the transaction service provider. Thetransaction message (e.g., first authorization request) may include theaccount information associated with the virtual payment device (e.g.,PAN or token associate therewith, cardholder name, expiration date, cvvcode, and the like), as well as other information relevant forprocessing the payment transaction.

At step S11, the transaction service provider system 22 may communicatean authorization request including at least a portion of the transactionmessage to the issuer 1 system 24 a operated by or on behalf of theissuer.

With continued reference to FIG. 10 , at step S12, the issuer 1 system28 a may determine an authorization decision associated with the paymenttransaction (e.g., approve, decline, some combination thereof, and/orthe like). For example, the issuer 1 system 28 a may determine that theauthorization decision is to approve the payment transaction.

At step S13, the issuer 1 system 28 a may communicate the authorizationresponse including the authorization decision (e.g., to approve thepayment transaction) to the transaction service provider system 22. Atstep S14, the transaction service provider system 22 may communicate atransaction response including the authorization decision to themerchant system 20 (e.g., directly or via an acquirer).

At step S15, the merchant system 20 may communicate the authorizationdecision to the e-wallet application 14. At step S16, the e-walletapplication 14 may cause the user device 12 to display for the user thatthe payment transaction is approved.

With continued reference to FIG. 10 , and at some point duringprocessing of the payment transaction (e.g., prior to the authorizationdecision, during settlement of the payment transaction, etc.), at stepS17, the e-wallet application 14 may cause a graphical user interfacefor prompting a user to indicate whether the rewards amount (or aportion thereof) is to be redeemed to be displayed on the user device 12(see e.g., FIG. 7 ). At step S18, the user may input into the graphicaluser interface displayed by the user device 12 (e.g., in the e-walletapplication 14) that at least a portion of the rewards amount availablefor the virtual payment device is to be applied to the paymenttransaction.

At a step S19, the e-wallet application 14 may communicate a redemptionrequest to the TSP rewards processor 26. The redemption request mayinclude the rewards amount or portion thereof indicated to be used bythe user.

At step S20, the TSP rewards processor 26 may communicate the redemptionrequest to the issuer 1 rewards system 28 a. Issuer 1 rewards system 28a may process the redemption request by applying the requested rewardsamount to the payment transaction.

At step S21, the issuer 1 rewards system 28 a may communicate to the TSPrewards system 26 a redemption response including an updated rewardsamount available for the virtual payment device after application of therequested rewards amount to the payment transaction. At step S22, theTSP rewards system 26 may communicate the rewards response including theupdated rewards amount to the e-wallet application 14.

At step S23, the e-wallet application 14 may cause the updated rewardsamount to be displayed by the user device 12 (see FIG. 8 ). For example,as shown in FIG. 8 , a $50.50 rewards amount (5050 rewards points)associated with the virtual payment device was applied to the paymenttransaction, such that $49.50 remains as the rewards amount (4950rewards points) available for the virtual payment device. The updatedrewards amount may be used by the user towards future paymenttransactions initiated using the virtual payment device.

Although the disclosure has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred embodiments, it is to be understood that suchdetail is solely for that purpose and that the disclosure is not limitedto the disclosed embodiments, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present disclosure contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

What is claimed is:
 1. A computer-implemented method, comprising:determining a rewards amount associated with a virtual payment device bycommunicating between a user device of a user and a rewards managementsystem comprising a transaction service provider system of a transactionservice provider and an issuer reward system of an issuer and notcomprising a merchant system of a merchant with which paymenttransactions may be initiated using the virtual payment device, whereinthe user device comprises an electronic wallet application storing atoken associated with the virtual payment device of the user issued tothe user by the issuer of an issuer system, the token corresponding tobut different from an account identifier of the virtual payment deviceprovided by the issuer, wherein determining the rewards amountassociated with the virtual payment device comprises: receiving, by thetransaction service provider system, a first rewards inquiry from theelectronic wallet application of the user device, the first rewardsinquiry comprising the token; retrieving, by the transaction serviceprovider system, the account identifier corresponding to the token froma tokenization system based on the first rewards inquiry; transmitting,by the transaction service provider system, a second rewards inquiry tothe issuer reward system, the second rewards inquiry comprising theaccount identifier; receiving, by the transaction service providersystem, a rewards inquiry response containing a rewards amountassociated with the virtual payment device from the issuer rewardsystem; and transmitting, by the transaction service provider system, atleast a portion of the rewards inquiry response to the user device tocause the rewards amount associated with the virtual payment device tobe displayed in the electronic wallet application; and redeeming areward amount regardless of the merchant system by communicating betweenthe user device and the rewards management system, wherein redeeming thereward amount comprises: during processing of a payment transaction,receiving, by the transaction service provider system and from theelectronic wallet application of the user device, a redemption requestspecifying a portion of the rewards amount to be applied to the paymenttransaction, the payment transaction processed between the user deviceand an electronic payment processing network separate from the rewardsmanagement system, the electronic payment processing network comprisesthe merchant system, the transaction service provider system, and theissuer system; and transmitting, by the transaction service providersystem, at least a portion of the redemption request to the issuersystem to apply the portion of the rewards amount to the paymenttransaction.
 2. The computer-implemented method of claim 1, whereinprocessing the payment transaction comprises: in response to theelectronic wallet application initiating the payment transaction,receiving, by the transaction service provider system, an authorizationrequest message; and processing, by the transaction service providersystem, the authorization request message over the electronic paymentprocessing network.
 3. The computer-implemented method of claim 2,wherein processing the authorization request message comprises:transmitting, by the transaction service provider system, at least aportion of the authorization request message to the issuer system;receiving, by the transaction service provider system, an authorizationresponse message containing an authorization decision from the issuersystem; and transmitting, by the transaction service provider system, atleast a portion of the authorization response message to the userdevice.
 4. The computer-implemented method of claim 1, wherein theelectronic wallet application stores the token, but does not store theaccount identifier.
 5. The computer-implemented method of claim 1,wherein the account identifier comprises an original account identifier.6. The computer-implemented method of claim 1, wherein the issuer of theissuer reward system and the issuer of the issuer system is a sameissuer, wherein the same issuer is the issuer of the virtual paymentdevice.
 7. The computer-implemented method of claim 1, furthercomprising: generating, by the transaction service provider system, thesecond rewards inquiry by replacing the token of the first rewardsinquiry with the account identifier.
 8. A system comprising at least oneprocessor programmed or configured to: determine a rewards amountassociated with a virtual payment device by communicating between a userdevice of a user and a rewards management system comprising atransaction service provider system of a transaction service providerand an issuer reward system of an issuer and not comprising a merchantsystem of a merchant with which payment transactions may be initiatedusing the virtual payment device, wherein the user device comprises anelectronic wallet application storing a token associated with thevirtual payment device of the user issued to the user by the issuer ofan issuer system, the token corresponding to but different from anaccount identifier of the virtual payment device provided by the issuer,wherein determining the rewards amount associated with the virtualpayment device comprises: receiving, by the transaction service providersystem, a first rewards inquiry from the electronic wallet applicationof the user device, the first rewards inquiry comprising the token;retrieving, by the transaction service provider system, the accountidentifier corresponding to the token from a tokenization system basedon the first rewards inquiry; transmitting, by the transaction serviceprovider system, a second rewards inquiry to the issuer reward system,the second rewards inquiry comprising the account identifier; receiving,by the transaction service provider system, a rewards inquiry responsecontaining a rewards amount associated with the virtual payment devicefrom the issuer reward system; and transmitting, by the transactionservice provider system, at least a portion of the rewards inquiryresponse to the user device to cause the rewards amount associated withthe virtual payment device to be displayed in the electronic walletapplication; and redeem a reward amount regardless of the merchantsystem by communicating between the user device and the rewardsmanagement system, wherein redeeming the reward amount comprises: duringprocessing of a payment transaction, receiving, by the transactionservice provider system and from the electronic wallet application ofthe user device, a redemption request specifying a portion of therewards amount to be applied to the payment transaction, the paymenttransaction processed between the user device and an electronic paymentprocessing network separate from the rewards management system, theelectronic payment processing network comprises the merchant system, thetransaction service provider system, and the issuer system; andtransmitting, by the transaction service provider system, at least aportion of the redemption request to the issuer system to apply theportion of the rewards amount to the payment transaction.
 9. The systemof claim 8, wherein processing the payment transaction comprises: inresponse to the electronic wallet application initiating the paymenttransaction, receiving, by the transaction service provider system, anauthorization request message; and processing, by the transactionservice provider system, the authorization request message over theelectronic payment processing network.
 10. The system of claim 9,wherein processing the authorization request message comprises:transmitting, by the transaction service provider system, at least aportion of the authorization request message to the issuer system;receiving, by the transaction service provider system, an authorizationresponse message containing an authorization decision from the issuersystem; and transmitting, by the transaction service provider system, atleast a portion of the authorization response message to the userdevice.
 11. The system of claim 8, wherein the electronic walletapplication stores the token, but does not store the account identifier.12. The system of claim 8, wherein the account identifier comprises anoriginal account identifier.
 13. The system of claim 8, wherein theissuer of the issuer reward system and the issuer of the issuer systemis a same issuer, wherein the same issuer is the issuer of the virtualpayment device.
 14. The system of claim 8, wherein the at least oneprocessor is programmed or configured to: generate, by the transactionservice provider system, the second rewards inquiry by replacing thetoken of the first rewards inquiry with the account identifier.
 15. Acomputer program product comprising at least one non-transitorycomputer-readable medium including one or more instructions that, whenexecuted by at least one processor, cause the at least one processor to:determine a rewards amount associated with a virtual payment device bycommunicating between a user device of a user and a rewards managementsystem comprising a transaction service provider system of a transactionservice provider and an issuer reward system of an issuer and notcomprising a merchant system of a merchant with which paymenttransactions may be initiated using the virtual payment device, whereinthe user device comprises an electronic wallet application storing atoken associated with the virtual payment device of the user issued tothe user by the issuer of an issuer system, the token corresponding tobut different from an account identifier of the virtual payment deviceprovided by the issuer, wherein determining the rewards amountassociated with the virtual payment device comprises: receiving, by thetransaction service provider system, a first rewards inquiry from theelectronic wallet application of the user device, the first rewardsinquiry comprising the token; retrieving, by the transaction serviceprovider system, the account identifier corresponding to the token froma tokenization system based on the first rewards inquiry; transmitting,by the transaction service provider system, a second rewards inquiry tothe issuer reward system, the second rewards inquiry comprising theaccount identifier; receiving, by the transaction service providersystem, a rewards inquiry response containing a rewards amountassociated with the virtual payment device from the issuer rewardsystem; and transmitting, by the transaction service provider system, atleast a portion of the rewards inquiry response to the user device tocause the rewards amount associated with the virtual payment device tobe displayed in the electronic wallet application; and redeem a rewardamount regardless of the merchant system by communicating between theuser device and the rewards management system, wherein redeeming thereward amount comprises: during processing of a payment transaction,receiving, by the transaction service provider system and from theelectronic wallet application of the user device, a redemption requestspecifying a portion of the rewards amount to be applied to the paymenttransaction, the payment transaction processed between the user deviceand an electronic payment processing network separate from the rewardsmanagement system, the electronic payment processing network comprisesthe merchant system, the transaction service provider system, and theissuer system; and transmitting, by the transaction service providersystem, at least a portion of the redemption request to the issuersystem to apply the portion of the rewards amount to the paymenttransaction.
 16. The computer program product of claim 15, whereinprocessing the payment transaction comprises: in response to theelectronic wallet application initiating the payment transaction,receiving, by the transaction service provider system, an authorizationrequest message; and processing, by the transaction service providersystem, the authorization request message over the electronic paymentprocessing network.
 17. The computer program product of claim 16,wherein processing the authorization request message comprises:transmitting, by the transaction service provider system, at least aportion of the authorization request message to the issuer system;receiving, by the transaction service provider system, an authorizationresponse message containing an authorization decision from the issuersystem; and transmitting, by the transaction service provider system, atleast a portion of the authorization response message to the userdevice.
 18. The computer program product of claim 15, wherein theelectronic wallet application stores the token, but does not store theaccount identifier.
 19. The computer program product of claim 15,wherein the account identifier comprises an original account identifier.20. The computer program product of claim 15, wherein the issuer of theissuer reward system and the issuer of the issuer system is a sameissuer, wherein the same issuer is the issuer of the virtual paymentdevice.